Closed
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the CHANGELOG.md to replace legacy "Kairo" references with the current "Agent 365" SDK name, ensuring consistency with the project's current naming conventions.
Changes:
- Updated the top-level SDK description from "Microsoft Kairo SDK" to "Microsoft Agent 365 SDK"
Comments suppressed due to low confidence (5)
CHANGELOG.md:11
- The package name still contains "Kairo" and should be updated to use "Agent 365" terminology. This is a legacy reference that needs to be updated according to the project's naming guidelines which specify that all "Kairo" references should be removed or replaced.
- **Microsoft.Kairo.Sdk.DevTools.Analyzer.SemanticKernel** - Comprehensive Roslyn analyzer package for enforcing Agent365 governance patterns
CHANGELOG.md:34
- This SDK name reference still uses "Kairo" and should be updated to "Microsoft Agent 365 SDK" for consistency with the updated description at line 3.
- Initial release of Microsoft Kairo SDK
CHANGELOG.md:36
- The extension method name reference uses "Kairo" and should be updated to reflect the current Agent 365 SDK naming conventions.
- `Kairo` extension methods for `IHostApplicationBuilder` configuration
CHANGELOG.md:37
- The class name "KairoSpanProcessor" contains the legacy "Kairo" keyword and should be documented using the updated naming convention consistent with Agent 365 SDK.
- `KairoSpanProcessor` for custom span processing with agent-specific metadata
CHANGELOG.md:41
- The class name "KairoOpenTelemetryScope" contains the legacy "Kairo" keyword and should be documented using the updated naming convention consistent with Agent 365 SDK.
- `KairoOpenTelemetryScope` base class for extensible tracing
pontemonti
approved these changes
Jan 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.